-
Notifications
You must be signed in to change notification settings - Fork 393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove failed libraries on running clusters #956
Conversation
Whenever a library fails to get installed on a running cluster, we automatically remove it, so that the clean state of managed libraries is properly maintained. Without this fix users had to manually go to Clusters UI and remove library from a cluster, where it failed to install. Libraries add up to CREATE and UPDATE timeouts of `databricks_cluster` resource. Fixes #599
Codecov Report
@@ Coverage Diff @@
## master #956 +/- ##
==========================================
+ Coverage 85.66% 85.69% +0.03%
==========================================
Files 103 103
Lines 9060 9093 +33
==========================================
+ Hits 7761 7792 +31
- Misses 789 790 +1
- Partials 510 511 +1
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Messages []string `json:"messages,omitempty"` | ||
Library *Library `json:"library,omitempty"` | ||
Status string `json:"status,omitempty"` | ||
IsGlobal bool `json:"is_library_for_all_clusters,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we start deprecation of this flag? Because per documentation:
This option does not install the library on clusters running Databricks Runtime 7.0 and above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not changeable by users anymore 🤷🏻♂️ but there still might be some workspaces with dbr7.0, that have this
Whenever a library fails to get installed on a running cluster, we automatically remove it, so that the clean state of managed libraries is properly maintained. Without this fix users had to manually go to Clusters UI and remove library from a cluster, where it failed to install. Libraries add up to CREATE and UPDATE timeouts of
databricks_cluster
resource.Fixes #599